
              VB CodeSecure 4.0 README File


                         CONTENTS

1.  Introduction
2.  Installation
3.  Using VB CodeSecure
4.  Troubleshooting
5.  Shareware Notice
6.  Copyright Notice
7.  Disclaimer

INTRODUCTION

VB CodeSecure 4.0 is a useful program that protects Visual Basic 3.0
and Visual Basic 4.0 executables from any VB decompiler.  VB CodeSecure
protects your executable by using powerful data-protection algorithms.
These algorithms include form overlays, objects de-referencing and
control de-referencing.  By using any combination of the three protection
schemes provided by VB CodeSecure, your application's source code will
remain safe.

INSTALLATION

Installing VB CodeSecure is simple.  If you obtained VB CodeSecure by
downloading it off of an online service, BBS or the Internet, then
all you have to do is unzip the archive VBCS.ZIP into an empty directory.
The archive should contain these files:

VBCS.EXE     -  VB CodeSecure Executable File
VBCS.TXT     -  VB CodeSecure README File
VBCS.HLP     -  VB CodeSecure Help File
VBCS.ICO     -  VB CodeSecure Icon File
ORDER.FRM    -  VB CodeSecure Order Form
FILE_ID.DIZ  -  VB CodeSecure Information File
GAUGE16.OCX  -  16-bit Gauge OLE Control
THREED16.OCX -  16-bit 3D OLE Control
COMDLG16.OCX -  16-bit Common Dialog OLE Control

Note that GAUGE16.OCX, THREED16.OCX and COMDLG16.OCX should be moved into
your WINDOWS\SYSTEM directory if they are not already there.

The files above are not the only files that VB CodeSecure needs in order
to operate.  The files below are necessary to run this program as well as
any other Visual Basic 4.0 developed application.  If you program in any
edition of Visual Basic 4.0, you probably already have the following
necessary files located in your WINDOWS\SYSTEM directory.

VB40016.DLL
OC25.DLL
OLE2.DLL
TYPELIB.DLL
OLE2DISP.DLL
OLE2PROX.DLL
OLE2CONV.DLL
STORAGE.DLL
COMPOBJ.DLL
OLE2.REG
OLE2NLS.DLL
STDOLE.TLB
SCP.DLL
VAEN21.OLB
CTL3DV2.DLL

Failure to have all of the above files in your WINDOWS\SYSTEM directory
will result in an error saying that you are using the wrong version of
Windows for this program.

To obtain the files above, download them from CompuServe's MSBASIC forum.
GO MSBASIC and then download VB4R16S.ZIP from the forum's file libraries.

USING VB CODESECURE

After you've installed VB CodeSecure, run VBCS.EXE.  VB CodeSecure has
now been started.  You can press F1 at any time to access online help.

In order to protect your application against decompiling, all you have to
do is follow these six easy steps:

1.  Select your application's project file.
2.  Select your application's executable file.
3.  Specify the path to your application's form files.
4.  Choose whether you developed your program in Visual Basic 3.0 or
    Visual Basic 4.0.
5.  Choose any combination of the three protection schemes you want to use
    to protect your executable.
6.  Toggle any other options you want and then begin protection.

That's how easy it is to produce a final decompile-proof VB executable 
with VB CodeSecure.

Selecting Your Project File

To select your application's project file, click on Select Project File
from the Project menu.  A dialog box will open up.  Choose the name of 
your application's project file and click OK.

Selecting Your Executable File

To select your application's executable file, click on Select Executable
File from the Project menu.  A dialog box will open up.  Choose the name
of your application's executable file and click OK.

Selecting Your Project Path

When you select your application's project file, VB CodeSecure attempts
to retrieve the path to your application's form files.  If this path is
incorrect, you should retype it in the Project Path text box.  Please 
note that all of your application's form files MUST be saved in ASCII
format (not binary) in order for VB CodeSecure to operate properly.

Configuring VB CodeSecure

You can configure VB CodeSecure's options two different ways.  You
can access the Options menu and then click on the option you want
to configure and toggle between the choices.  You can also configure
VB CodeSecure by choosing Custom Configuration from the Options
menu.

The quickest and easiest way to configure VB CodeSecure is to choose 
Custom Configuration from the Options menu.  A dialog box will pop up.
In this dialog box, there are several options that need to be changed 
so that VB CodeSecure can operate properly.

You should first specify your compiler type.  If you developed your
application in Visual Basic 3.0 Standard or Professional Editions, then
you should choose Visual Basic 3.0.  If you developed your application
in Visual Basic 4.0 Standard, Professional or Enterprise Editions 16-bit
or 32-bit, then you should choose Visual Basic 4.0.

Next, choose the protection schemes you want to use on your application.
You can choose from Overlay Forms, De-reference Objects and De-reference
Controls.  Overlay Forms and De-reference Objects work the best together.
De-referencing your application's controls is not recommended and should
only be used if all other protection schemes fail.

Next, you should choose the speed you want VB CodeSecure to run at. The
three available speeds are Most Accurate, Normal and Fastest.  Most Accurate
is the default and it is recommended that you keep the speed at this always
for best results.  Most Accurate uses a non-linear searching method unlike
Normal and Fastest.  Normal and Fastest use linear searching which
substantially speeds up processing time if your executable file is lengthy
and/or your CPU is slow, but your executable will most likely not be fully
protected.

Now all that is left is to configure is Use Meter Bars and Backup Original
EXE options.  If you want to see a meter bar under the progress window
when you begin protection, then enable this option.  If you want to backup
your executable file before attempting to protect it, then enable the
Backup Original EXE option.  VB CodeSecure saves your original EXE to
the file EXE.BAK in the directory you installed VB CodeSecure to.

Now that all options have been configured, click on Save and then click on
the Begin button or Begin Protection from the Project menu.  If you don't
want to save the current options, click Cancel.

Another dialog box will appear when you choose Begin.  Your application
is already undergoing protection.  You will see a window called the Progress
Window.  You will also see a meter bar if Use Meter Bar was checked as well
as a Pause button.  The Progress Window shows what processes your
application is undergoing in order to protect it.  If you want to pause
protection, then click the Pause button.  You should never pause protection
unless it is absolutely necessary.

You'll notice that after protection has been started, your application will
be processed in a very short time.  After your application has been
processed, you will be notified whether or not VB CodeSecure successfully
protected your executable and you will be prompted whether or not you want
to test your application to see if it is functioning properly.  If you 
choose Yes to test your application, VB CodeSecure will run your 
application's executable.  Then, VB CodeSecure will prompt you whether
or not you think your application is functioning properly.  If you choose
Yes, then VB CodeSecure's job is done and now your executable is safe 
from decompiling.  If you choose No, then VB CodeSecure will restore your
executable back to it's original form as long as you enabled the Backup
Original EXE option.

VB CodeSecure then terminates whether it has protected your executable or
not due to the large amount of data it has to handle.  Future versions
of the program will fix this problem.

For more help on VB CodeSecure, press F1 while you are in the program or
choose Contents from the Help menu.  Be sure to also check the
Troubleshooting section below if you have a specific problem.

TROUBLESHOOTING

For the most part, using VB CodeSecure is very self-explanatory.  However,
there are some specific problems you may encounter along the way.  Below
are common questions about VB CodeSecure that are answered in full.

Q:  Anytime I click Begin to protect my executable I receive an Overflow
    message.  Why does this happen?

A:  This problem occurs when your application's form files are not saved
    in ASCII format.  All of your application's form files MUST be saved
    in ASCII format in order for VB CodeSecure to obtain the necessary data.

Q:  I received an incorrect Windows version message when I tried to run
    the program.  Do I need a Win32 OS to run this program?

A:  No, you do not need a Win32 OS to run this program.  The program
    was developed using Windows 95, but VB CodeSecure is a 16-bit program.
    You probably need the Visual Basic 4 16-bit supplementary files which
    are available from CompuServe's MSBASIC forum.  The files are stored
    in VB4R16S.ZIP in the forum's file libraries.

Q:  My application didn't run properly after it was protected.  What can I
    do to make it run properly and still be protected?

A:  Try using just one protection scheme instead of a combination of the
    three that are available.  In addition, set the speed to Most Accurate.

If you had a problem that could not be answered by this file or the help
file, then you should contact the developer of VB CodeSecure, Jason Clay
at one of the following e-mail addresses:

CompuServe:  75453,3331
Internet:    75453.3331@compuserve.com

SHAREWARE NOTICE

You currently have the shareware version of VB CodeSecure 4.0.  The
shareware version can only protect executables up to 25k in length
and must contain 3 or less forms.

Please feel free to distribute the shareware version to online services,
BBS's and the Internet.  If you want to distribute VB CodeSecure on CD-ROM
media, you must receive consent from the author, Jason Clay.

The registered version of VB CodeSecure can protect executables of
unlimited length and can contain an unlimited number of forms.
Registered users are also entitled to unlimited FREE technical
support via e-mail and low-cost upgrades.

To order the latest version of VB CodeSecure, you must fill out and
send the order form (ORDER.FRM) along with $25 to:

	Jason Clay
	c/o Innovative Tech Inc.
	4108 Dilts Lane
	Bridgewater, NJ  08807

You can order VB CodeSecure by cash, check or money order.
All checks must be payable to Jason Clay.  For orders on 3.5" disk,
please include an additional $3 for shipping and handling.

CompuServe members can easily register online by accessing the SWREG
forum.  GO SWREG and search under product ID 12602 or search under author
75453,3331.  Select VB CodeSecure and fill out the requested information.
A fee of $30 will be added to your monthly CompuServe bill when you
register using this method.

If you have any questions about registering, feel free to e-mail me at
one of these e-mail addresses:

CompuServe:  75453,3331
Internet:    75453.3331@compuserve.com

COPYRIGHT NOTICE

VB CodeSecure 4.0
Copyright 1996 Jason Clay, Innovative Tech Inc.  All Rights Reserved.

DISCLAIMER

THIS SOFTWARE IS SOLD "AS IS".  INNOVATIVE TECH INC., JASON CLAY
OR ANY OF THEIR CLIENTS WILL NOT BE RESPONSIBLE FOR ANY DAMAGES
RESULTING FROM THE MISUSE OF THIS PROGRAM.  YOU, THE USER ARE TO
TAKE FULL RESPONSIBILITY FOR ANY DAMAGES OCCURING TO YOUR SYSTEM
WITH THE USE OF THIS PROGRAM, VB CODESECURE 4.0.
